Configure Device Data Collection and Monitoring Options

First create a network policy.

This task is part of the network policy configuration workflow. Use this task to set the following data collection and monitoring options:

  • Application Visibility and Control (AVC): AVC gives you information that can help you manage network traffic and applications. AVC detects the application-layer contents of the frame to determine the application or protocol that is transmitting the data. ExtremeCloud IQ can then track the amount of data being transmitted by a particular application or protocol.
  • Device Wireless Activity Thresholds: Set activity threshold limits above which event alarms are generated.
  • Client Wireless Activity Thresholds: These alarms identify when violations occur that affect the wireless health of a client as reported in SLA reports for non-compliant clients. To trigger more alarms, lower thresholds. To reduce the number of alarms, increase thresholds.
  • Kernel Diagnostic Data Recorder (KDDR): KDDR logs capture run-time statistical data about unexpected events for Extreme Networks devices. Extreme Networks Support analyzes the content of these binary log files for troubleshooting.
  • Automatic Synthetic Traffic Generation: Some of the Client 360, Device 360 and Network 360 monitoring capabilities require synthetic traffic generation.
  1. Go to Configure > Network Policies.
  2. Select an existing policy, and then select Edit, or select Add.
  3. After you save the Policy Details, select NEXT or 2 Wireless.
  4. From the Application Management menu, select Device Data Collection And Monitoring.
  5. Toggle the Application Visibility and Control setting ON to detect frame application-layer contents.
  6. Toggle the Statistics Collection setting ON to record wireless activity statistics between the device and connected clients.
  7. To change the data collection interval, select the number of minutes from the menu.
  8. For Device Wireless Activity Thresholds, type values for the following fields:
    • CRC error rate exceeds: The point at which the percent of CRC errors in received wireless frames during the collection interval is considered to be excessive.
    • Tx drop rate exceeds: The point at which the percent of transmitted wireless unicast frames that a device drops during the collection interval is considered excessive. A transmitted wireless frame is dropped when the device tries to transmit the same unicast frame a maximum number of times without receiving an acknowledgment from the intended recipient.
    • Rx drop rate exceeds: The point at which the percent of dropped wireless frames during collection interval is considered excessive. A device might drop wireless frames on its ingress Wi-Fi interface for several reasons, such as the arrival of duplicate frames or frames that cannot be decrypted.
    • Tx retry rate exceeds: The point at which the percent of retransmitted wireless frames during the collection interval is considered excessive. A device tries to resend a unicast frame if the first effort does not elicit an acknowledgment from its intended recipient.
    • Airtime Consumption exceeds: The point at which the percent of transmitted and received airtime usage for a wireless interface during the collection interval exceeds the maximum airtime consumption threshold.
  9. For Client Wireless Activity Thresholds, type values for the following fields:

    Tx drop rate exceeds: Indicates the point at which the percent of wireless unicast frames that a device drops during transmission to the same client during the statistics collection interval is considered excessive.

    Rx drop rate exceeds: Indicates the point at which the percent of dropped wireless frames received from the same client during the statistics collection interval is considered excessive.

    Tx retry rate exceeds: Indicates the point at which the percent of retransmitted wireless frames to the same client during the collection interval is considered excessive.

    Airtime Consumption exceeds: Indicates the point at which the percent of airtime that a device consumes while transmitting traffic to and receiving traffic from the same client during the collection interval is considered excessive.

  10. Toggle the Kernel Diagnostic Data Recorder setting ON to capture run-time statistical data about unexpected events.
  11. For Automatic Synthetic Traffic Generation:
    1. Enable RADIUS Authentication to create synthetic traffic.
    2. Toggle the Check Radius service connectivity via Status-Server setting ON to check RADIUS service connectivity.

      Ensure that Status-Server is enabled on the RADIUS server.

    3. Adjust the check Interval if necessary.
9038986-00 Rev AA